Management of pharmacy kits

ABSTRACT

A system for managing pharmacy kits comprises a reading station configured to read tag information from a plurality of radio frequency identification (RFID) tags associated with a pharmacy kit, and an information processing system operatively connected to the reading station and configured to receive the tag information from the reading station and determine a status of the pharmacy kit based on the tag information, a plurality of stored templates defining contents to be included in each of a plurality of pharmacy kits, and a plurality of kit records indicating the current contents of a plurality of pharmacy kits.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/554,342 filed on Jul. 20, 2012, which claims priority to U.S.Provisional Application No. 61/514,231 filed on Aug. 2, 2011, each ofwhich is incorporated herein by reference in its entirety.

BACKGROUND

Hospital pharmacies often manage groups of medical items in the form ofpharmacy kits. A pharmacy kit can be used, for instance, to provide agroup of items for a specific medical procedure, a particular physician,or a designated location of a hospital. As an example, a pharmacy kitcan be used to aggregate and transport a collection of medicines fortreating a patient with a specific type of stroke, heart condition, orother ailment.

A pharmacy kit (or “kit”) typically comprises a group of items specifiedby a template. For example, the template may specify that the kitrequires three vials of adenosine, two containers of albuterol solution,two vials of amiodarone, and so on. The template may also specify waysin which individual items may be satisfied. For example, it may specifythat the vials of adenosine may be satisfied by certain product brands.Pharmacy kits are usually stocked by a hospital pharmacy, but they maybe stocked by another entity, such as an outsourced kit stockingcompany.

Local board-of-pharmacy regulations (e.g., state regulations) typicallyallow a hospital or other facility to define the contents of its kits.In other words, they allow the hospital to create its own templates.These regulations, however, also require that the hospital adhere to atemplate once defined. This typically requires specific procedures toensure accuracy of kit contents. Such procedures can include, forinstance, regulated kit creation and inventory procedures, andprescribed monitoring and/or update procedures. The following areexamples of such procedures as used in certain conventional contexts.

A kit is typically created by receiving specified items in a pharmacy,manually recording (e.g., on paper and/or electronic records) theirproduct identifiers (e.g., National Drug Code (NDC) or Universal ProductCode (UPC)), lot numbers, and expiration dates, and then loading theitems into a container, such as a box, tray, or canister. During thekit's lifetime, it may be updated periodically to replace expired orconsumed items. These updates are typically performed by manuallyinspecting the kit, comparing it to a corresponding template, modifyingkit contents as required, and then manually recording any changes.

Unfortunately, the above procedures tend to suffer from significantshortcomings. For instance, the manual recording of item information isgenerally time consuming and error prone, which drives up the cost ofcreating and updating the kits. Moreover, these procedures are usuallyperformed by highly trained pharmacy staff, which may be an inefficientuse of their time. Manual inspections for missing, expired, orsoon-to-be expired items can also be time consuming and error prone,particularly because item expiration dates tend to vary betweendifferent products within the same kit.

Due to the above and other shortcomings, there is a general need forimproved techniques and technologies for managing pharmacy kits.

SUMMARY

According to one embodiment of the inventive concept, a system formanaging pharmacy kits comprises a reading station configured to readtag information from a plurality of radio frequency identification(RFID) tags associated with a pharmacy kit, and an informationprocessing system operatively connected to the reading station andconfigured to receive the tag information from the reading station anddetermine a status of the pharmacy kit based on the tag information, aplurality of stored templates defining contents to be included in eachof a plurality of pharmacy kits, and a plurality of kit recordsindicating the current contents of a plurality of pharmacy kits.

According to another embodiment of the inventive concept, a method ofmanaging pharmacy kits comprises operating an RFID reader to read taginformation from a plurality of RFID tags associated with a pharmacykit, identifying a plurality of items present in the pharmacy kit basedon the tag information, and comparing the plurality of items with anelectronic template to determine a status of the pharmacy kit.

According to another embodiment of the inventive concept, a methodcomprises building a pharmacy kit comprising a plurality ofpharmaceutical items labeled with RFID tags, verifying contents of thepharmacy kit by operating an RFID reader to read tag information fromthe RFID tags and comparing the tag information with an electronictemplate, deploying the pharmacy kit within a facility following theverification, and re-verifying the contents of the pharmacy kitfollowing the deployment by operating an RFID reader to read taginformation from the RFID tags and comparing the tag information withthe electronic template.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings illustrate selected embodiments of the inventive concept.In the drawings, like reference numbers indicate like features.

FIG. 1 is a block diagram of a system for managing pharmacy kitsaccording to an embodiment of the inventive concept.

FIGS. 2A through 2C are diagrams illustrating a pharmacy kit accordingto an embodiment of the inventive concept.

FIGS. 3A and 3B are diagrams of a read station in the system of FIG. 1according to an embodiment of the inventive concept.

FIG. 4 is a diagram of an information processing system in the system ofFIG. 1 according to an embodiment of the inventive concept.

FIG. 5 is a flowchart illustrating a method of managing pharmacy kitsaccording to an embodiment of the inventive concept.

FIG. 6 is a flowchart illustrating a method of receiving and processingitems for a pharmacy kit according to an embodiment of the inventiveconcept.

FIG. 7 is a flowchart illustrating a method of building a pharmacy kitaccording to an embodiment of the inventive concept.

FIGS. 8A and 8B are flowcharts illustrating methods of operating thesystem of FIG. 1 according to an embodiment of the inventive concept.

FIG. 9 shows an interface that can be used to control the system of FIG.1 according to an embodiment of the inventive concept.

FIG. 10 shows a report generated for a pharmacy kit using the system ofFIG. 1 according to an embodiment of the inventive concept.

FIG. 11 shows another report generated for a pharmacy kit using thesystem of FIG. 1 according to an embodiment of the inventive concept.

FIG. 12 shows an interface for checking out a kit to a user or locationaccording to an embodiment of the inventive concept.

FIGS. 13A and 13B show interfaces used to generate and view reportsregarding pharmacy kits according to an embodiment of the inventiveconcept.

FIGS. 14A through 14D are diagrams of a label that can be used to attachan RFID tag to various items of a pharmacy kit according to anembodiment of the inventive concept.

DETAILED DESCRIPTION

Embodiments of the inventive concept are described below with referenceto the accompanying drawings. These embodiments are presented asteaching examples and should not be construed to limit the scope of theinventive concept.

The described embodiments relate generally to management of pharmacykits (hereafter, “kits”) such as those commonly used in hospitalenvironments or other medical facilities. Such kits can be distinguishedgenerally from other types of kits used by hospitals, such as surgicalinstrumentation kits, electronic equipment kits, and so on, due to theunique nature of pharmaceutical products. For example, pharmaceuticalproducts may be regulated very different from the items in surgical kitsdue to the need to constantly monitor expiration dates, and also due tothe substitutability of some pharmaceutical products for others.

In certain embodiments, a kit management system uses RFID technology tolabel and track the contents of a kit. The use of RFID technology canallow a pharmacy to accurately and efficiently determine whether itemsin the kit are consumed, missing, expired, or near expiration. Thesedeterminations can be used thereafter to verify and update the kitcontents, track item usage patterns, generate patient billinginformation based on item consumption, and so on.

In certain embodiments, a hospital pharmacy begins by tagging items uponbulk receipt in the hospital, or when a kit is stocked. Alternatively,items may arrive at a hospital pre-tagged. One way to tag the items isby scanning bar codes present on most items used in a kit, printing RFIDtags based on the scanned bar codes, and then applying the RFID tags tothe items. The scanned bar codes typically provide item information suchas product identifiers (e.g., NDC or UPC), lot numbers, and expirationdates. This information can be associated with the RFID tags in acomputer database to allow subsequent identification and processing byRFID technology. In some embodiments, the RFID tags can be generatedautomatically when scanning the bar codes, e.g., through the use of anRFID tag printer operatively connected to a bar code scanning machine.Alternatively, the RFID tags may be non-printed tags.

A kit is typically built by placing tagged items in a container such asa box, tray, or canister, and optionally labeling the kit with an RFIDtag having information such as a kit identifier, kit type, intendeduser, or location, for example. These steps are generally performed by apharmacist or other competent medical professional.

Once a kit is built, its contents are verified by placing it in an RFIDreading station, which reads all RFID tags within its sensing range toidentify the kit type and any items present. In some embodiments, theRFID reading station includes an enclosure such as a metal box to allowscanning of the kit exclusive of other RFID devices that may be in thesurrounding environment. Alternatively, the RFID reading station mayomit such an enclosure, for instance, by performing reading in an openarea such as table, or using a handheld RFID reader. If the kit has anRFID tag, the kit type can be determined from the tag. Otherwise, it maybe inferred from the items present. Items are typically identified byrecognizing their RFID tags and then accessing stored information thatmaps the RFID tags to specific item information.

The stored information may reside on electronic equipment located at theRFID reader station or a remote location such as a remote server, apersonal computer (PC), a mobile device, etc. In addition to basic kitand item information, the electronic equipment may also store metadatarelated to kit processes, such as who built or rebuilt a kit, what itemswere replaced if the kit was restocked, when the items were inserted inthe kit, when verification and update procedures were last performed orwill next be performed, and so on.

After the kit and item information are determined by the kit managementsystem, they are analyzed automatically with reference to one or moretemplates. For instance, a kit template may be located based on the kittype, and then the identified items may be compared with the kittemplate to determine whether any items are missing or requirereplacement based on use or expiration. Additionally, the informationprocessing system may analyze item information to determine whether anyitems are expired or will soon expire. The kit can then be updated basedon these analyses.

Kit templates are typically stored in a database within or associatedwith the information processing system. However, they can alternativelybe stored within a memory associated within the RFID reading station orRFID reader, or they can be stored in a separate system accessible bythe information processing system.

In general, expiration of an item may occur based on a fixed or variabletimeframe. For example, some items may expire at a fixed date indicatedby the manufacturer, while other items may expire after a certain amountof time out of the refrigerator, e.g., time of removal+X days. Whetherthe timeframe is fixed or variable can be indicated in the template at amaster level for a particular item, or at a segment level for a segmentincluding the item.

The automatic processing provided by RFID technology and associatedelectronic equipment allows kit management to be performed with greaterefficiency and accuracy compared with conventional approaches. Forinstance, in some embodiments, kit contents and expiration dates can bevalidated in 15 seconds or less. Moreover, kit deficiencies can bereported to a pharmacist automatically, allowing them to be addressed inan efficient manner. This reporting can be accomplished, for instance,by an automatically generated charge sheet showing kit contents andexpirations.

Once a kit is built and verified, it is ready to be sealed and deployedfor use in the hospital. When a kit is used, the seal is broken anditems may be removed or consumed. Accordingly, the kit may besubsequently returned to the RFID reading station for additionalverification, monitoring, and updates. These additional procedures canbe used, for example, to determine whether any items in the kit aremissing (e.g., due to use), and whether any items are erroneouslypresent in the kit. This information can then be used to generate areport indicating the status and any necessary updates for the kit, orfor other purposes such as patient billing or supply ordering. Once therelevant information is collected, the kit can be rebuilt using theautomatically generated report, and then redeployed for another use.

Stored item and kit information can also be used to perform variousforms of monitoring and/or reporting related to inventory management.For instance, stored kit information can be analyzed to identifypatterns of item consumption. Moreover, the stored information can beinspected to determine the location of kits containing expired items.These and other forms of monitoring and/or reporting can be performedeither automatically or in response to user input. For instance, theycan be performed according to a predetermined schedule or in response tocertain event triggers. Alternatively, a user may simply requestmonitoring or a report as needed. For example, a pharmacy manager maylog in to view consumption logs, usage logs, and current inventory tomake more informed decisions on which inventory to keep and which kitsmay require special attention.

The kit management system typically further comprises a user interfaceand one or more software applications allowing a user to accessinformation regarding the status of kits. As an example, a softwareapplication may be used to generate and print a kit charge sheet orcharge sheet with the contents and expiration dates of the items and akit. As other examples, a software application may be used to generateinventory reports showing where kits are dispatched within a hospital,an expiration report indicating dispatched items that are expired ornear expiration, consumption, and usage reports with traceability todepartments, code types, or patients. The kit management system can alsocomprise or be integrated with a real-time tracking system to maintaincurrent information regarding kit locations. The real-time trackingsystem typically comprises electronic components associated with thekits and configured to transmit information from the kits to theinformation processing system to identify the kits' respectivelocations. Such tracking systems can also be combined with kitmanagement software in order to update the information used to generateinventory reports.

As indicated by the foregoing, a kit management system according tocertain embodiments can provide many potential benefits compared withconventional technologies. For example, the kit management system canprovide more efficient verification and recording of kit contents, andmore accurate monitoring of kits, items, and expiration dates. Incertain embodiments, the kit management system may also provide dataanalysis capabilities for purposes such as patient billing, inventorytracking, and so on.

FIG. 1 is a block diagram of a system 100 for managing pharmacy kitsaccording to an embodiment of the inventive concept.

Referring to FIG. 1, system 100 comprises an information processingsystem 115 and an RFID reading station 110. System 100 is configured toautomatically read and process information from a pharmacy kit 105. Thisallows relatively efficient monitoring and updating of the kit'scontents.

RFID reading station 110 comprises an RFID reader configured to readRFID tags located on kit 105. During a typical read operation, the RFIDreader interrogates RFID tags associated with respective items in kit105, and it also interrogates any RFID tag associated with kit 105. As aconsequence of the interrogation, the RFID reader receives informationidentifying each tag, and it conveys the information to informationprocessing system 115. Based on the tag information, informationprocessing system 115 identifies kit 105 and the items present. This canbe accomplished, for instance, by relating the tag information to itemor kit information stored in a computer database.

Once the kit and items are identified, information processing system 115may process corresponding information in various ways, for example, bydisplaying it to a user, generating reports indicating missing orexpired items, performing patient billing procedures based on anyconsumed items, or merely storing it for subsequent analysis. In certainembodiments, the kit and item information is managed as a list. Forexample, it can be stored and accessed in the form of a list in acomputer database or other storage medium.

System 100 may occasionally aggregate last known status information foreach kit that has been read, and it may then determine whether anyaction is required to resolve expiration issues, missing item issues, orextra item issues in all of the kits in a hospital or other facility.These actions can be performed, for example, on a periodic basis, inresponse to particular events, or in response to a user request.

In addition to storing the current or most recent information regardingthe kits, system 100 may also store a virtual history for each kit. Sucha virtual history may include, for example, a record of each transactioninvolving the kit since the time it was tagged. Such transactions mayinclude, for example, scans, database queries, updates such asrestocking or removal of items, and so on. The virtual history may bemaintained by information processing system 115, for example, and it maybe output in the form of a report in response to a user request. Inaddition, the virtual history may be used to gather data or statisticsthat may be useful for planning future tasks such as kit updates, itemrestocking, and so on.

Kit 105 can be associated to a location or responsible person, such as aphysician. This association can then be stored in system 100, and it canbe used to quickly determine the location of kit 105 after deployment.The location of kit 105 can also be determined and/or updated byassociating its RFID tag with a real time location system. In addition,kit 105 may be associated with a patient identifier or billingidentifier and any missing items may be marked as being consumed by thatbilling or patient identifier. Such billing information may be storedeither in system 100, in a separate system or in both system 100 and aseparate system. System 100 may retrieve or update some or all of thebilling information when a kit is read and items may or may not beconsumed.

Where kit 105 contains prescription pharmaceuticals, the facility may berequired to comply with requirements set by a state board of pharmacy.The precise regulations may vary from state to state, but can includerequirements such as a mandatory visual inspection of kit 105 prior todeployment, or an item-by-item determination of each item type, lotnumber and expiration date. Other board of pharmacy requirements mayinclude documentation to be included in kit 105 to verify completenessand accuracy of expiration data or a label on the outside of kit 105 toindicate the last check of the kit and the next expiring item in thekit.

In some embodiments, system 100 is configured to store relevant board ofpharmacy requirements and verify that each step has been completed.System 100 can also be configured to compute steps automatically whereallowed by regulations. Such steps may include, for example, printingdocumentation or labels, reading tags and verifying items, or requestingconfirmation that a manual step has been completed. As these steps arecompleted, system 100 may record the name of the person who performedthe steps. It may also confirm whether the person is authorized toperform the steps. In general, information regarding these and othersteps can be recorded in system 100 using a log, database, or otherstorage format.

Although FIG. 1 shows RFID reading station 110 and informationprocessing system 115 as separate features, they are not required to bephysically or functionally separate. For instance, informationprocessing features could be integrated with parts of RFID readingstation 110, such as an RFID reader. In general, the physical andfunctional implementation of system 100 can be partitioned arbitrarilybetween various forms of hardware, software, firmware, etc., as will berecognized by those skilled in the art.

In addition, the physical and functional implementation of system 100can be distributed arbitrarily across multiple devices, systems, ornetwork components. For example, in some embodiments, informationprocessing system 115 may include or be integrated with wireless mobiledevices in order to convey information remotely. One potential use ofsuch a configuration would be to transmit kit notifications to remoteusers via push email or SMS text messaging, or subscription based datafeeds. Such notifications could be used, for instance, to alert usersthat an updated kit is available, that a kit should be returned to thepharmacy, that a checked-out kit requires updates due to itemexpiration, and so on. Another potential reason to integrate informationprocessing system 115 with remote components is to receive updates ofkit templates and item master data. For example, some or all of a kittemplate or item master data may be received from an external system.The received item master data could indicate, for example, that an itemhas been recalled or changed in some material respect.

FIGS. 2A through 2C are diagrams illustrating a pharmacy kit accordingto an embodiment of the inventive concept. In particular, FIG. 2A showsan example of a kit tray comprising multiple items having RFID tags,FIG. 2B shows an example of a partial template associated with the kit,and FIG. 2C shows an example of a partial kit record for the kit. Thekit of FIGS. 2A through 2C represents one example of pharmacy kit 105shown in FIG. 1.

Referring to FIG. 2A, kit 105 comprises a container 205 and items 210.Container 205 is shown as a tray in FIG. 2A, but this is merely oneexample of a container that can be used to carry items 210. Alternativeexamples include boxes, canisters, bags, coolers, and various others.Although not shown in FIG. 2A, kit 105 could further comprise a cover,such as a lid, that can be used to enclose items 210 prior todeployment. Additionally, the cover can be sealed onto container 205 toprevent tampering between deployment and use of kit 105. In general,where kit 105 is susceptible to opening or closing (e.g., where it has alid or other covering), it can be read in an open configuration or aclosed configuration.

Items 210 typically include medicines or other medical supplies that maybe stocked by a pharmacy. As shown in FIG. 2A, items 210 can havevarious different forms of packaging. For example, they can be packagedin vials, bags, boxes, bottles, and other forms. These different formsof packaging may also comprise different materials, such as glass,plastic, paper, cardboard, foam, or metal.

Due to the different types of packaging and materials, items 210 may betagged with RFID tags having different shapes or types. As one example,RFID tags placed on metal bags may be subject to electromagneticinterference (EMI) from the metal. Accordingly, to prevent EMI, RFIDtags connected to metal bags may have a foam backing or other form ofinsulation to create separation from the bags. Such tags may be referredto as metal-mount tags. As another example, RFID tags attached to smallvials or bottles may potentially occlude label information on the vials.Accordingly, to prevent occlusion, RFID tags having a transparentadhesive portion may be attached to vials, bottles, or other types ofpackages. Such tags may be referred to as transparent tags.

Kit 105 is typically built by manually placing items 205 in container210. This is typically accomplished by a pharmacist or other competentmedical professional after items 205 have been labeled with RFID tagsand stocked in the pharmacy. For example, a pharmacist may visitpharmacy shelves to collect items 205 and place them in container 210.

Referring to FIG. 2B, an example template defines items to be placed inkit 105. More specifically, the template defines a plurality of itemsegments (or “segments”) to be included in kit 105, where each itemsegment corresponds to a class or type of items and/or additionalsegments to be included in specific quantities. For instance, an itemsegment may define a specific class of medications, such as ibuprofen,acetaminophen, adenosine, or albuterol. Where a segment includes one ormore additional segments, the template is considered to have multiplesegment “levels”. In general, a template can have an arbitrary number ofsegment levels. An example of a template having multiple segment levelswould be one containing a segment “analgesic”, with the item “morphine”and a sub-segment “ibuprofen” containing items “Advil” and “Generic”.

For simplicity, FIG. 2B shows example segments in generic form, i.e.,“medicine bottle 1”, “medicine vial 2”, etc. The segment “medicinebottle 1”, for example, indicates that kit 105 is to include one or morebottles of a first type of medicine (e.g., a bottle of ibuprofen).Similarly, the segment “medicine vial 2” indicates that kit 105 is toinclude one or more vials of a second type of medicine (e.g., a vial ofadenosine), and so on. Although each segment in FIG. 2B is associatedwith a particular type of packaging, such as a bottle, vial, or bag,segments are not necessarily limited by package type. For instance, asegment could be defined more broadly based on medicine type alone.

The template further defines a set of permissible items that can be usedto satisfy each segment. The permissible items may correspond todifferent brands or other forms of each item corresponding to thesegment. These items are generally identifiable by distinct NDC or UPCidentifiers. As an example, a segment defined as a “bottle of ibuprofen”may be satisfied by a either a bottle of Advil or a bottle of genericibuprofen. For simplicity, FIG. 2B shows the items associated with eachsegment in generic form, i.e., “product A”, “product B”, etc.Accordingly, the segment “medicine bottle 1” may be satisfied by twodifferent products “A” and “B”, the segment “medicine vial 2” may besatisfied by three different products “C”, “D”, and “E”, and so on.

The template still further defines a quantity of items to be included inkit 105 for each segment. For example, based on the template of FIG. 2B,kit 105 is to include one item corresponding to “medicine bottle 1”(e.g., one bottle of ibuprofen), three items corresponding to “medicinevial 2”, two items corresponding to “medicine bag 3”, and so on. As amore concrete example, a segment “Pain Medication” could havepermissible items “Tylenol” or “Advil”, with a quantity of two, whichcould be satisfied by two bottles of Tylenol, two bottles of Advil, orone of each, for instance.

In general, the quantity can be zero or more. Where the quantity isgreater than one, each item of a particular segment can be satisfied byany combination of the permissible items for that segment. For example,if there are three permissible items and the required quantity is three,the requirement may be satisfied by three of the same permissible item,one of each, etc. For instance, some kits may allow the stock ofadenosine vials to be satisfied by different product brands.Alternatively, the template may require that multiple instances of thesame item be selected, or that only certain combinations of items arepermitted. Moreover, the template may include restrictions on the itemsthat can be included in combination from among different segments.

Although the template determines the contents to be included in the kitunder most circumstances, there are occasions where deviation from thetemplate will be permitted. One of these occasions is a nationalshortage of one or more items to be included in the kit. When there is anational shortage of a particular item, certain substitutions oromissions of the item may be allowed. For example, if sodium bicarbonateis on national shortage, a kit may be permitted to include a suitablesubstitute for sodium bicarbonate, or it may be permitted to be deployedwithout sodium bicarbonate or any substitute.

The procedure for managing items under shortage may be defined in avariety of ways. For example, allowable substitutes for nationalshortage conditions may be embedded in the template itself and thentriggered by information processing system 115 when a shortage arises.As an alternative example, information processing system 115 may simplyignore certain restrictions in a template when a shortage arises.

Referring to FIG. 2C, a kit record comprises information regarding thecontents of a kit that has been built in a pharmacy and verified throughthe use of RFID reading station 110. In the example of FIG. 2C, theinformation comprises the name of each segment in the kit, and specificdetails of each item in each segment. The specific item details includea brand name, an item name, an NDC identifier, a lot number, medicinestrength or concentration, and an expiration date. The item details mayfurther include information indicating whether an item has a fixedexpiration date or one that varies based on time away from arefrigerator. Where the item has a variable expiration date, the itemdetails may indicate whether the item has been removed from therefrigerator, and if so, at what time or date.

The kit record is typically generated by RFID reading station 110 orinformation processing system 115 upon verifying or re-verifying thekit. It can then be compared to a corresponding template to determinewhether the kit has missing or expired items, or it can be stored ininformation processing system 115 for subsequent comparisons, updates,or analyses.

FIGS. 3A and 3B are diagrams of RFID reading station 110 of FIG. 1according to an embodiment of the inventive concept. In particular, FIG.3A is a block diagram illustrating electronic equipment associated withRFID reading station 110 according to an example embodiment, and FIG. 3Bis a schematic diagram of a container configured to receive kit 105during a read operation of RFID reading station 110.

Referring to FIG. 3A, RFID reading station 110 comprises an RFID reader305 and an antenna 310. Antenna 310 is located within a container 315designed to receive kit 105 during a read operation. RFID reader 305controls antenna 310 to communicate with RFID tags associated with itemsof kit 105, as well as any RFID tag associated with the kit itself. Inaddition, RFID reader 305 receives and processes communications receivedby antenna 310 from kit 105. Although RFID reader 305 is shown outsideof container 315, it could alternatively be included within container315. Moreover, although RFID reader 305 and antenna 310 are shown as twoseparate components, they could alternatively be integrated into asingle component or divided into additional components.

In a typical read operation, RFID reader 305 controls antenna 310 tointerrogate any RFID tags within container 315. In response to theinterrogation, the RFID tags communicate information to RFID reader 305via antenna 310. The communicated information is typically associatedwith corresponding information stored in a database, such as NDCidentifiers, lot numbers, and expiration dates for individual items, anda kit identifier for the kit as a whole. RFID reader 305 communicatesthe received information to information processing system 115 forstorage and/or comparison with a template.

Referring to FIG. 3B, container 315 comprises an enclosed space forreceiving kit 105. The left side of FIG. 3B shows container 315 withdoors opened to receive kit 105, and the right side of FIG. 3B showscontainer 315 with doors closed to perform a read operation. The use ofan enclosed space to allows RFID tags to be read without interferencefrom objects in the surrounding environment, such as false positivesfrom RFID tags on items not belonging to kit 105. Accordingly, container315 may be formed of a material designed to provide electromagneticshielding, such as a metal box.

In some embodiments, RFID reading station 110 is restricted to receivingonly one kit at a time. This restriction may be imposed in a variety ofways, for instance, by configuring an enclosure to accommodate only onekit container or interrogating kit tags prior to scanning to ensure thatno more than one kit tag is present. In certain alternative embodiments,RFID reading station 110 may be specifically configured to allowconcurrent scanning of multiple kits. For example, two kits could beplaced in RFID reading station 110, scanned concurrently, and thenassigned to a common location or person, such as a particular cart,room, physician, etc. Moreover, such a common assignment may be recordedin information processing system 115 to allow joint analysis or trackingof more than one kit.

FIG. 4 is a diagram of information processing system 115 according to anembodiment of the inventive concept. In the embodiment of FIG. 4,various features of information processing system 115 are connected in anetworked configuration. However, in alternative embodiments thesecomponents could be in alternative configurations, e.g., with componentsdirectly connected, physically integrated, or functionally partitionedin other ways.

Referring to FIG. 4, information processing system 115 comprises acomputer 405 and a server 420. Computer 405 and server 420 are connectedto each other via the internet 415, and computer 405 is connected to anRFID reader, a bar code reader, and an RFID printer through a local areanetwork (LAN) 435.

Computer 405 comprises a browser 410 that receives kit information fromthe RFID reader via LAN 435 and communicates with server 420 through theinternet 415. Server 420 stores templates 425, which typically includekit master templates and item master templates. Server 420 also storesrecords 430, which include information regarding individual kits anditems.

Although server 420 is shown as a single unit in FIG. 4, it may comprisemore than one device, such as multiple local and/or central computers.In addition, although server 420 is shown to be connected with a singlecomputer, it may be connected to additional or alternative devices, suchas other local computers, mobile devices, and so on. Moreover, althoughserver 420 is shown to receive information from a single RFID reader, itcould also receive information from other RFID readers. For example,information processing system could be connected to multiple RFIDreading stations through the internet 415.

The RFID printer can be used to print RFID tags automatically when a kitis being built or updated. For example, an RFID tag can be printed for anew item by scanning the item's bar code using a bar code scannerconnected to computer 405, accessing server 420 to associate aparticular RFID tag with the item, and then printing the RFID tag.

FIG. 5 is a flowchart illustrating a method of managing pharmacy kitsaccording to an embodiment of the inventive concept. The method of FIG.5 is typically performed by a pharmacist or other medical professionalassociated with a hospital pharmacy. For explanation purposes, it willbe assumed that the method of FIG. 5 is performed using system 100 ofFIG. 1. However, the method is not limited to a particular system. Inthe description that follows, example method steps will be indicated byparentheses (XXX) to distinguish them from device or system components.

Referring to FIG. 5, the method begins with a pharmacy receiving andprocessing kit items (505). The items typically arrive in bulk at thepharmacy and are processed by tagging them with RFID tags and recordingthem in an inventory system. Next, a kit is built from tagged items inthe pharmacy inventory (510), and the kit is scanned using RFID readingstation 110 (515). The scan detects RFID tags of kit items and the kititself and transmits corresponding information to information processingsystem 115.

Information processing system 115 updates stored records to reflect thescanning (520). In the update, a database in information processingsystem 115 is updated to reflect the scanned kit contents. For example,the database may be updated to reflect the presence of any new orreplaced items, along with their expiration dates. The database may alsobe updated with other information, such as the name of the person wholast modified the kit contents, a location to which the kit is to bedeployed, a patient to be billed for consumption of kit items, and soon.

Based on the updated records, information processing system 115 performsa status check to verify the contents of the kit (525). The status checktypically involves forming a list of items based on the transmittedinformation or updated records and comparing the list against a kittemplate. It may also involve comparing the updated kit informationagainst information obtained in prior scans, or evaluating the kitinformation in light of certain business rules, such as billingprotocols.

If the status check indicates a deficiency in the kit(525=“Deficiency”), such as missing or expired items, the kit contentsare updated (530), and the method returns to step 515 where the kit isre-scanned. The update can be performed, for example, by replacing anyexpired items or inserting missing items. Otherwise, if the status checkindicates no deficiency in the kit (525=“No Deficiency”), the kit isdeployed for use in the hospital or other facility served by thepharmacy (535).

The updating of records and status check are typically performed anytime the kit is scanned, as indicated by the flow of FIG. 5. This cantake place under a variety of circumstances, such as when a kit is firstbuilt and verified, when the kit is checked-in to the pharmacy forstorage, or when the kit is checked-out of the pharmacy for use.

Deployment of the kit may involve, for example, transporting it to aspecific location of the hospital, checking it out to a particularindividual, or merely storing it within the pharmacy. Followingdeployment, steps 515 through 535 may be repeated any number of times asneeded. For example, the kit may be re-scanned and updated followingeach use or it may be periodically updated at specified times, such asdaily, weekly, or whenever an expired item is noted in informationprocessing system 115.

FIG. 6 is a flowchart illustrating a method of receiving and processingitems for a pharmacy kit according to an embodiment of the inventiveconcept. The method of FIG. 6 is an example of step 505 of FIG. 5.

Referring to FIG. 6, items arrive at a facility (e.g., a hospital) froma third party manufacturer, distributor, or supplier (605). In somecircumstances, the items may have RFID tags when they arrive at thefacility. Accordingly, system 100 may scan the items and look up iteminformation from the third party or an additional third party. Suchinformation may include, for example, item master data, item lot data,and item expiration dates. If the items are not already tagged, iteminformation may be entered into system 100 using a bar code scanner asdescribed above, or by manual user input (610).

Based on the item information, system 100 determines whether each itemrequires a first type of tag (illustrated as type “A”) or a second typeof tag (illustrated as item type “B”) (615). This determination istypically performed based on the type of the item or its packaging. Forexample, items having metal packaging such as metal bag, etc., mayrequire an RFID tag having a thicker insulation layer (e.g., foam) toprevent it from experiencing EMI from the metal. Other types of items,such as glass or plastic packages, may not require such an RFID tag.Although the method of FIG. 6 shows an example using two different tagtypes, the described method is not limited to two tag types, and couldbe performed with additional tag types. Following the determination ofthe tag type, system 100 creates the first type of tag (620) or thesecond type of tag (625).

In creating the tags, system 100 may optionally perform automaticdetection of whether it is attached to an RFID printer. If such anattachment is detected, it may control the RFID printer to print an RFIDtag having a unique identifier for each item in the kit. Otherwise, auser may manually enter a unique tag identifier for each item intosystem 100. The manually entered identifiers can be determined, forexample, based on the labeling of already printed RFID tags.

Next, system 100 associates the unique identifiers with the stored iteminformation (630), allowing the item information to be retrievedsubsequently when the RFID tags are scanned. Finally, the RFID tags areattached to corresponding items (635).

FIG. 7 is a flowchart illustrating a method of building a pharmacy kitaccording to an embodiment of the inventive concept. The method of FIG.7 is an example of step 510 of FIG. 5.

Referring to FIG. 7, the method comprises inserting tagged items into acontainer (705), generating an RFID tag for the kit (710), and applyingthe RFID tag to the kit (715). The method may further comprise sealingthe kit; however, the sealing is typically performed after the kit hasbeen scanned. Where system 100 is connected to an RFID printer, thekit's RFID tag can be generated using the printer, similar to the methodof FIG. 6. Otherwise, a preprinted RFID tag can be used, and the tag'snumber can be manually entered into system 100 as in the method of FIG.6. The sealing can be performed, for example, using a shrink wrapmaterial, an adhesive, a sticker, or various other known techniques. Ingeneral, the term seal or sealing, as used herein, should not beconstrued in an overly formal sense—for example, it does not require anairtight seal—but rather it merely refers to a mechanism for ensuringthat the contents of the kit are not tampered with as long as a sealremains in place or unbroken. Moreover, some seals used in conjunctionwith RFID technology may allow RFID based detection of whether a seal isbroken.

FIGS. 8A and 8B are flowcharts illustrating methods of operating kitmanagement system 100 according to an embodiment of the inventiveconcept. In particular, FIG. 8A shows a method that can be used toimplement step 515 of FIG. 5, and FIG. 8B shows a method that can beused to implement parts of the method of FIG. 8A.

Referring to FIG. 8A, a user or sensor initiates an RFID read operation(805). This can be accomplished, for instance, by merely placing kit 105in RFID reading station 115, or by actuating specific controls on a userinterface. In the read operation, RFID reader 305 powers antennas ofRFID tags in kit 105, and it reads item tags and a kit tag, if present(810). The read operation may be used to perform an initial inventory ofkit 105 following its assembly, or it can used for a re-inventoryfollowing use. Next, tag data is sent to a server in informationprocessing system 115 or elsewhere (815). Finally, the server reportsinformation to a user via an interface such as a computer display or acomputer-generated printout (820).

Referring to FIG. 8B, steps 805 and 815 can be performed through the useof a web interface such as a web browser. For example, in someembodiments, a user directs a computer to request a web page from aserver (825). This is typically accomplished through a web browser andit can be done in an encrypted or non-encrypted manner. For instance,the computer can communicate with the server using an encrypted protocolsuch as the secure sockets layer (SSL) protocol.

Next, the server returns instructions on how to scan which could takethe form of a link allowing control of the RFID reader (830). In theexample using a link, the user clicks on the link to start a readoperation, and the RFID reader then captures tag information from kit105 and transmits it to the computer (835). Finally, the computer relaysthe tag information to the server for validation, storage, and/or otherforms of processing (840).

The server typically stores kit-related information such as mastertemplates, item master templates, and information regarding individualkits and items, as in the example of FIG. 4. This information can becompared with the tag information relayed to the server in step 840, andthen based on the comparison the server may generate a report on thestatus of the kit, such as whether any items are absent or whether anyitems have been erroneously included in the kit. The report may alsoinclude information relating to the expiration status of the items inkit 105, such as whether the items are expired or near expiration, or asummary of the expiration status of a set of items or the kit as awhole. The report may also include a charge sheet including the statusof each item, such as its expiration date, which items have expired,which items are about to expire, and which item is going to expire next.In general, the information included in the report may be data that wasread from a kit, item, or other source, or it may be data that wascalculated based on rules, inputs, or other criteria.

FIG. 9 shows an interface 900 that can be used to control system 100according to an embodiment of the inventive concept. For example,interface 900 can be used to control various aspects of the methodsillustrated in FIGS. 5 through 8. Interface 900 is typically accessedthrough a display connected to a computer or server such as thoseillustrated in FIG. 4.

Referring to FIG. 9, interface 900 comprises interactive graphical userinterface (GUI) components including a menu bar 905 and buttons 910through 925. These features allow a user to initiate various kit-relatedprocedures, such as scanning a kit that has been placed in an RFIDreading station, generating reports based on kit information, printingRFID tags for a kit, and performing administrative tasks. For example, auser may press button 910 (or alternatively, a scan button in menu bar905) to initiate a read operation of RFID reading station 110 after kit105 has been placed in a designated reading location such as a metalbox. The user may press button 915 to generate a report comprisinginformation similar to that illustrated in FIG. 2C. The user may pressbutton 920 to initiate a procedure for capturing item information andprinting RFID tags. Finally, the user may press button 925 to accessvarious administrative controls for system 100 or interface 900.

FIG. 10 shows a report 1000 generated for a pharmacy kit using system100 according to an embodiment of the inventive concept. Report 1000corresponds to a pediatric emergency drug tray, which is a type of kitcomprising items used for common pediatric emergencies. Such a kit canbe deployed to a hospital emergency room, for example.

Referring to FIG. 10, report 1000 comprises a portion 1005 indicatingthe type of kit for which the report was generated, as well as the totalnumber of items in the kit. In this example, the kit comprises 51 totalitems. Report 1000 further comprises a portion 1010 indicating thenumber of extra and missing items in the kit, as well as the number ofexpired or soon to expire items. In this example, one item is missingand two items are near expiration. The soon-to-expire items are listedas two containers of Procainamide Hydrochloride, which expire on Oct. 1,2012. The date range of soon-to-expire items can be set arbitrarily, forexample, using administrative tools accessible through button 925 ininterface 900. Nevertheless, the date range is typically established inconsideration of factors such as the anticipated delay betweendeployment of the kit and its use, as well as any regulatoryconsiderations, such as rules from the board-of-pharmacy requirements orthe joint commission (TJC).

Report 1000 also includes a portion 1015 indicating the date of a mostrecent scan, a portion 1020 showing additional details for thesoon-to-expire items, and a portion 1025 showing additional details formissing items.

FIG. 11 shows another report 1100 generated for a pharmacy kit usingsystem 100 according to an embodiment of the inventive concept. Report1100 corresponds to a demonstration kit, which is a type of kitcomprising items used for common pediatric emergencies. Such a kit canbe deployed to a hospital emergency room, for example.

Report 1100 comprises a portion 1105 indicating the type of the kit andthe total number of items in the kit. In this example, the kit comprises26 total items. Report 1100 further comprises a portion 1010 indicatingthe number of extra and missing items in the kit, an entity to be billedfor used items, and the number of expired or soon to expire items. Inthis example, there are two extra items, one expired item, and onesoon-to-expire item. The entity to be billed is listed as KRE1981. Theexpired item is a box of Protopic, which is listed as having expired onSep. 28, 2012.

Report 1100 further comprises a portion 1115 indicating the date of amost recent scan, a portion 1120 showing additional details for theexpired items, a portion 1125 showing additional details for thesoon-to-expire items, and a portion 1130 showing additional details forthe extra items. Report 1100 still further comprises a portion 1135indicating a current location of the kit and providing a “check out”button for assigning the kit to a specific location or person. In thisexample, the kit is currently assigned to the location “CentralPharmacy”.

FIG. 12 shows an interface 1200 for checking out a kit to a user orlocation according to an embodiment of the inventive concept. Interface1200 can be invoked, for instance, using the check out button in area1135 of FIG. 11. In response to a user pressing the check out button, adialog box 1205 appears within interface 1200. Dialog box 1205 allows auser to select a person or place to whom the kit may be assigned. Thisselection can be made, for example, as the kit is placed in possessionof the selected person or an authorized delivery agent. Informationregarding the selected person and location can then be stored in system100 to facilitate subsequent recovery or further monitoring of the kit.

FIGS. 13A and 13B show interfaces 1300A and 1300B used to generate andview reports for pharmacy kits according to an embodiment of theinventive concept. In particular, FIG. 13A shows an example of aninterface where a user has selected to view a report of kits that needre-working, and FIG. 13B shows an example of an interface where a userhas selected to view a report of kits containing a specific lot number.

Referring to FIG. 13A, interface 1300A comprises a first area 1305Awhere a user selects a type of report to be generated. In this example,the user has selected from a drop down menu to generate a report of kitsthat need re-working. Once the selection is made the drop down menu,first area 1305A is further populated with options of details to includein the report. In this example, the options allow the user to selectwhether the report should include surplus items, shortages, expireditems, expiring items, or all segments of the kit.

Interface 1300A further comprises a second area 1310A for displaying thereport. According to the report in area 1310A, system 100 hasinformation on two kits satisfying the specified options. In particular,a demo kit has a shortage of nasal spray, and it has a soon-to-expirecontainer of Gentamicin Sulfate. A bandage kit has shortages of small,medium, and large bandages.

Referring to FIG. 13B, interface 1300B comprises a first area 1305Bwhere a user selects the type of report to be generated. In thisexample, the user has selected from the drop down menu to generate areport of kits containing a specific item or lot number. Based on thisselection, first area 1305B is populated with a form allowing the userto enter all or part of a lot number or other information foridentifying the item. In the example of FIG. 13B, the user has entered alot number.

Interface 1300B further comprises a second area 1310B for displaying thereport. According to the report in area 1310B, a demo kit includes anitem with the lot number specified in second area 1310A. Notably, in theexample of FIG. 13B, only a partial lot number is entered first area1310B, so second area 1310B displays information related to items thatbegin with the partial lot number. However, system 100 could be modifiedto use the exact lot number only. It could also be modified to usemultiple lot numbers.

In addition to generating reports such as those illustrated in FIGS. 10through 13, system 100 may also generate reports on kit locations. Suchlocations can be determined, for example, through automatic kit trackingor some other mechanism. Moreover, system 100 may also providemechanisms for automatically tracking inventory in the kits and theusage of items based on usage data. For example, by analyzing usage dataof different items, system 100 could determine the level inventory tomeet minimum requirements of all kits in a facility or a target level ofinventory to be maintained. For example, if a type of kit requires abottle of ibuprofen and the facility has 20 kits of that type, thefacility has a minimum requirement of 20 bottles of ibuprofen. If thefacility uses 10 bottles of ibuprofen during a specified time (e.g., amonth), system 100 could then estimate or predict when the facility willrun out of the current stock of ibuprofen. Accordingly, system 100 canbe used to predict where inventory shortages may occur and then alertrelevant personnel of potential existing or upcoming inventoryshortages.

System 100 may also automatically inventory items in pharmacy kits todetermine where anything is missing, extra, expired, or near expired.This can reduce the chance of manual kit stocking errors or relatedmedical errors in a hospital or other facility. System 100 may alsoautomatically find items for recall in the hospital or emergency medicalfield kits.

FIGS. 14A through 14D are diagrams of a label 1400 that can be used toattach an RFID tag to various items of a pharmacy kit according to anembodiment of the inventive concept. In particular, FIG. 14A shows label1400 in a configuration prior to use, and FIG. 14B shows label 1400 in aconfiguration for attachment to a pharmaceutical item. FIG. 14C shows anexample of label 1400 with example dimensions and an embedded RFIDdevice 1435, and FIG. 14D shows label 1400 in the context of a printableroll.

Label 1400 is designed such that it can be securely attached todifferent types of items in a pharmacy kit without occluding labelinginformation. For example, label 1400 can be used in such a way that ithangs off the side of a vial, ampule, or other product where it may beinappropriate to place the main portion of the label directly on theproduct or product packaging. Alternatively, label 1400 can be attachedto an item such that it does not hang off the side. A configurationwhere a portion of label 1400 hangs off the side of an item will bereferred to as a “flagged” configuration.

Referring to FIG. 14A, label 1400 comprises a first portion 1405 havinga printed portion 1410 and a flap portion 1415 separated by aperforation indicated by a dotted line. Label 1400 further comprises asecond portion 1420 having a tail 1425 attached to first portion 1405,and a backing 1430 designed to be removed when tail 1425 is adhered toan item.

First and second portions 1405 and 1420 both have an adhesive backing.Accordingly, where label 1400 is used in the flagged configuration,adhesive backing portions of printed portion 1410 and flap portion 1415may be folded together along the perforation to prevent them fromsticking to other objects. Where label 1400 is not used in the flaggedconfiguration (e.g., when it is attached to a boxed item), first andsecond portions 1405 and 1420 may both be adhered to an item. Moreover,where label 1400 is not used in the flagged configuration, flap portion1415 may be removed by detaching it from printed portion 1410 along theperforation.

Printed portion 1410 and flap portion 1415 are typically formed with asubstrate material comprising a common labeling material such as paperor plastic. Printed portion 1410 further comprises an embedded RFIDdevice attached to the substrate. An example of such an RFID device isshown by RFID device 1435 in FIG. 14C. The substrate material can beprinted with identifying information for an item. Among the printedinformation, there may be a bar code for backward compatibility, orhuman-readable information related to the item or label 1400. The RFIDdevice can be encoded with identifying information through RFIDprinting.

The adhesive side of tail 1425 can be used to attach label 1400 to a kititem. Prior to use, the adhesive side is attached to backing 1430. Tail1425 is typically formed of a transparent material to avoid obscuringinformation on the items in a kit. In general, when labeling medicalitems such as pharmaceuticals, it is important not to obscure labels,warnings, and other information on the packaging. The use of atransparent tail 1425 avoids this problem by allowing the user to seethrough any portion of the tail that may be attached to an item.Moreover, the shape of tail 1425 and allows an RFID tag to be attachedto and/or hang off items having various different types of packaging. Asexamples, tail 1425 can be wrapped around a vial or ampule whileallowing first portion 1405 to hang off. Similarly, it can be attachedto a face of a box or a panel of a bag.

As alternatives to the example of FIG. 14A, the size of the tail mayvary, and the perforated portion may be omitted. The tail size, forexample, may be at least as large as the printable labeling portion.

Referring to FIG. 14B, label 1400 is shown in a configuration used toattach it to an item, which is illustrated conceptually by a dottedrectangle. When label 1400 is attached to the item, flap portion 1415 isadhered over printed portion 1410, and tail 1425 is adhered to the itemwhile first portion 1405 hangs off of it.

Referring to FIG. 14C, label 1400 may have example dimensions as shown.However, these dimensions may vary in alternative embodiments. Inaddition, label 1400 may comprise RFID 1435 as shown, although otherdevices or device configurations can be used in alternative embodiments.

Referring to FIG. 14D, label 1400 is shown in the context of a rollcomprising successive printable labels that can be fed into an RFIDprinter. In particular, label 1400 is shown as a second label amongthree successive labels “label 1”, “label 2”, and “label 3”. Theselabels are separated from each other by a small gap having a verticalsense mark used for alignment with an RFID printer.

The foregoing is illustrative of embodiments and is not to be construedas limiting thereof. Although a few embodiments have been described,those skilled in the art will readily appreciate that many modificationsare possible in the embodiments without materially departing from thenovel teachings and advantages of the inventive concept. Accordingly,all such modifications are intended to be included within the scope ofthe inventive concept as defined in the claims.

What is claimed is:
 1. A system for managing a pharmacy kit, comprising:a plurality of radio frequency identification (RFID) tags coupled to aplurality of pharmacy item containers, wherein the plurality of pharmacyitem containers are configured to store a plurality of pharmacy items,and wherein a first RFID tag of the plurality of RFID tags comprises: aprintable portion including an RFID device, and a tail portion formed ofa transparent material and including an adhesive backing for affixingthe first RFID tag to a first pharmacy item container of the pluralityof pharmacy item containers, wherein the transparent material preventsocclusion of label information of the first pharmacy item container; andan information processing system communicatively coupled to a RFIDreader, the information processing system comprising computer-executableinstructions that when executed by one or more processors cause the oneor more processors to: receive tag information of the plurality of RFIDbased at least in part on an antenna emitting a radio signal at leastwithin a pharmacy kit container, verify a pharmacy kit using the taginformation, wherein to verify the pharmacy kit, the computer-executableinstructions when executed cause the one or more processors to determinewhether at least one of: at least one pharmacy item of the plurality ofpharmacy items satisfies an expiration threshold or is subject to arecall, and cause a display to display results of the verification ofthe pharmacy kit.
 2. The system of claim 1, wherein to verify theplurality of pharmacy items, the computer-executable instructions whenexecuted further cause the one or more processors to compare pharmacyitem data with a pharmacy kit template, wherein the pharmacy item datais associated with the tag information.
 3. The system of claim 2,wherein the pharmacy kit template specifies a group of pharmacy itemsthat form at least a portion of the pharmacy kit.
 4. The system of claim3, wherein to verify the pharmacy kit, the computer-executableinstructions when executed further cause the one or more processors toidentify one or more missing pharmacy items based at least in part onthe comparison of the pharmacy item data with the pharmacy kit template.5. The system of claim 1, wherein the computer-executable instructionswhen executed cause the one or more processors to determine whether theat least one pharmacy item satisfies the expiration threshold, whereinthe expiration threshold comprises at least one of: an expiration dateof the at least one pharmacy item or a date prior to the expiration dateof the at least one pharmacy item.
 6. The system of claim 1, wherein toverify the plurality of pharmacy items, the computer-executableinstructions when executed further cause the one or more processors todetermine whether a quantity of at least one pharmacy item of theplurality of pharmacy items satisfies a threshold quantity.
 7. Thesystem of claim 1, wherein the computer-executable instructions whenexecuted further cause the one or more processors to determine whetherthe at least one pharmacy item is subject to the recall.
 8. A method ofmanaging a pharmacy kit, comprising: receiving tag information of aplurality of RFID tags coupled to a plurality of pharmacy itemcontainers based at least in part on an antenna emitting a radio signalat least within a pharmacy kit container, wherein the pharmacy kitcontainer provides electromagnetic shielding, wherein the plurality ofpharmacy item containers are configured to store a plurality of pharmacyitems, and wherein a first RFID tag of the plurality of RFID tagscomprises: a printable portion including an RFID antenna, and a tailportion formed of a transparent material and including an adhesivebacking for affixing the first RFID tag to a first pharmacy itemcontainer of the plurality of pharmacy item containers, wherein thetransparent material prevents occlusion of label information of thefirst pharmacy item container; verifying a pharmacy kit using the taginformation, wherein said verifying the pharmacy kit comprisesdetermining whether at least one of: at least one pharmacy item of theplurality of pharmacy items satisfies an expiration threshold or issubject to a recall; and causing a display to display results of saidverifying the pharmacy kit.
 9. The method of claim 8, wherein saidverifying the plurality of pharmacy items further comprises comparingpharmacy item data with a pharmacy kit template, wherein the pharmacyitem data is associated with the tag information.
 10. The method ofclaim 9, wherein the pharmacy kit template specifies a group of pharmacyitems that form at least a portion of a pharmacy kit.
 11. The method ofclaim 10, wherein said verifying the plurality of pharmacy items furthercomprises identifying one or more missing pharmacy items of the pharmacykit based at least in part on said comparing the pharmacy item data withthe pharmacy kit template.
 12. The method of claim 8, wherein saidverifying the plurality of pharmacy items comprises determining whetherthe at least one pharmacy item satisfies the expiration threshold,wherein the expiration threshold comprises at least one of: anexpiration date of the at least one pharmacy item or a date prior to theexpiration date of the at least one pharmacy item.
 13. The method ofclaim 12, wherein the expiration date is the expiration date is based atleast in part on an amount of time since the at least one pharmacy itemwas removed from refrigeration.
 14. The method of claim 8, wherein saidverifying the plurality of pharmacy items comprises determining whetherthe at least one pharmacy item is subject to the recall.
 15. A systemfor managing a pharmacy kit, comprising: an information processingsystem communicatively coupled to a radio frequency identification(RFID) reader, the information processing system comprisingcomputer-executable instructions that when executed by one or moreprocessors cause the one or more processors to: receive tag informationof a plurality of RFID tags coupled to a plurality of pharmacy itemcontainers based at least in part on an antenna emitting a radio signalat least within a pharmacy kit container, wherein the plurality ofpharmacy item containers are configured to store a plurality of pharmacyitems, and wherein a first RFID tag of the plurality of RFID tagscomprises: a printable portion including an RFID antenna, and a tailportion formed of a transparent material and including an adhesivebacking for affixing the first RFID tag to a first pharmacy itemcontainer of the plurality of pharmacy item containers, wherein thetransparent material prevents occlusion of label information of thefirst pharmacy item container; verify a pharmacy kit using the taginformation, wherein to verify the pharmacy kit, the computer-executableinstructions when executed cause the one or more processors to determinewhether at least one of: at least one pharmacy item of the plurality ofpharmacy items satisfies an expiration threshold or is subject to arecall; and cause a display to display results of the verification ofthe pharmacy kit.
 16. The system of claim 15, wherein to verify theplurality of pharmacy items, the computer-executable instructions whenexecuted further cause the one or more processors to compare pharmacyitem data with a pharmacy kit template, wherein the pharmacy item datais associated with the tag information.
 17. The system of claim 16,wherein the pharmacy kit template specifies a group of pharmacy itemsthat form at least a portion of the pharmacy kit.
 18. The system ofclaim 17, wherein to verify the pharmacy kit, the computer-executableinstructions when executed further cause the one or more processors toidentify one or more missing pharmacy items based at least in part onthe comparison of the pharmacy item data with the pharmacy kit template.19. The system of claim 15, wherein the computer-executable instructionswhen executed further cause the one or more processors to determinewhether the at least one pharmacy item of the plurality of pharmacyitems satisfies an expiration threshold, wherein the expirationthreshold comprises at least one of: an expiration date of the at leastone pharmacy item or a date prior to the expiration date of the at leastone pharmacy item.
 20. The system of claim 15, wherein to verify theplurality of pharmacy items, the computer-executable instructions whenexecuted further cause the one or more processors to determine whether aquantity of each pharmacy item of the plurality of pharmacy itemssatisfies a threshold quantity.
 21. The system of claim 15, wherein thecomputer-executable instructions when executed further cause the one ormore processors to determine whether the at least one pharmacy item issubject to the recall.